Skip to content

chore(deps): bump python from 3.12-slim to 3.14-slim - #9

Closed
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/docker/python-3.14-slim
Closed

dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/docker/python-3.14-slim

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Sep 11, 2026

Copy link
Copy Markdown
Contributor

Warning

Cooldown could not be applied because no publication date was available from the registry.

Bumps python from 3.12-slim to 3.14-slim.

Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
  • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

Bumps python from 3.12-slim to 3.14-slim.

---
updated-dependencies:
- dependency-name: python
  dependency-version: 3.14-slim
  dependency-type: direct:production
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot Bot added dependencies Pull requests that update a dependency file docker Pull requests that update docker code labels Sep 11, 2026
@dependabot
dependabot Bot requested a review from TadMSTR as a code owner September 11, 2026 23:46
@dependabot dependabot Bot added dependencies Pull requests that update a dependency file docker Pull requests that update docker code labels Sep 11, 2026
@TadMSTR

TadMSTR commented Sep 13, 2026

Copy link
Copy Markdown
Owner

Evaluated 2026-09-13 — deferred, not rejected. Leaving this open so Dependabot keeps the digest current.

Compatibility is fine. The blocker is the CVE position, and it runs the opposite way to what we assumed.

Measured

Both images built --no-cache, Trivy run with release.yml's exact flags (--severity HIGH,CRITICAL --ignore-unfixed --exit-code 1):

Check (amd64) 3.12-slim 3.14-slim
Builds, all deps install yes yes
Full suite, in-container 346 passed, 2 skipped 346 passed, 2 skipped — identical
Smoke test: starts, serves /health yes yes
Trivy release gate exit 0 exit 1

The code runs on 3.14 and every compiled dep has a 3.14 wheel. But the gate fails:

HIGH  msgpack     GHSA-6v7p-g79w-8964   1.1.2  -> 1.2.1
HIGH  setuptools  CVE-2025-47273        70.3.0 -> 78.1.1

Both are pip's vendored bundle, not our dependencies — pip/_vendor/vendor.txt lists exactly those two versions. (setuptools isn't on the filesystem or importable at all; it's pip's vendored copy.) The two bases differ only in the pip they ship: 3.12-slim has pip 25.0.1 vendoring msgpack==1.1.0, which isn't flagged; 3.14-slim has pip 26.2.1 vendoring msgpack==1.1.2, which is.

Upgrading pip doesn't help — 26.2.1 is already current. Tested; still exits 1.

The premise for taking this doesn't hold

The plan cited the base image's 4 fixable HIGH CVEs as the reason to move. That's true of the base but not of the published image: the Dockerfile's apt-get upgrade -y layer exists to clear them and does. The built 3.12 image has zero fixable HIGH/CRITICAL. Measured against what actually ships, 3.14 is a regression.

(First pass suggested 3.12 carried 12 CVEs — that was a cached apt-get upgrade layer, not a real result. Corrected with --no-cache.)

arm64 was not verified

Separately and independently: release.yml triggers on tag push only, with no workflow_dispatch, so the two-architecture gate can't run without publishing. And forge has no qemu-aarch64 binfmt handler (buildx offers linux/amd64, linux/386 only), so arm64 can't be built or run here either. All evidence above is amd64-only. Shipping a base bump whose arm64 half has never run is the exact hole the v0.4.0 audit closed, so this wouldn't be takeable on the CVE finding alone.

To unblock

  1. Wait for a pip release vendoring msgpack>=1.2.1 — clears by itself, and 3.12 is supported to 2028-10.
  2. Drop pip from the runtime image via a multi-stage venv build — durable, immunises against this whole class, wants its own review.
  3. .trivyignore the two — defensible, but it's a suppression.

Tracked as vikunja#838, with the arm64 gap as vikunja#839.

@TadMSTR

TadMSTR commented Oct 7, 2026

Copy link
Copy Markdown
Owner

Deferred again (2026-10-06). It's being left open deliberately so the decision stays visible. The 3.14-slim image still fails the release Trivy gate on pip 26.2.1's vendored bundle (msgpack 1.1.2, setuptools 70.3.0, urllib3 2.7.0), and the arm64 half can't be verified outside a tag-triggered release. The durable fix is a runtime stage with no pip in it, which would be its own PR.

@dependabot @github

dependabot Bot commented on behalf of github Nov 13, 2026

Copy link
Copy Markdown
Contributor Author

Superseded by #48.

@dependabot dependabot Bot closed this Nov 13, 2026
@dependabot
dependabot Bot deleted the dependabot/docker/python-3.14-slim branch November 13, 2026 08:54
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies Pull requests that update a dependency file docker Pull requests that update docker code

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant